Workflow Dependency Tool

In This Topic...

Workflow configurations consist of numerous components, many of which have dependencies on other system components. Prior to making changes to a specific component, it is often necessary to first understand how it is being used elsewhere in the system.

The Workflow Dependency Tool is designed to display the dependencies between individual Fields and Triggers and other workflow components. This provides insight into how a modification to one of these components will impact other existing workflow configurations. This information is of particular interest to system configurators responsible for creating, maintaining, and updating workflow components to address business needs.

Notes: Only fields and triggers that are managed directly through Workflow Containers are currently supported. Fields and triggers configured for use within Master Covers, Document Templates, E-mail Templates, or Cross-Policy Data Configurations are not supported. Similarly, any fields or triggers that are configured to control any form of Versioning are not currently supported.

In order to view the Check Dependencies button, and subsequently access the Workflow Dependency Tool, the Workflow must first be published.

Design

The purpose of the Workflow Dependency Tool is to highlight the dependencies between Fields and Triggers and other workflow resources. To best capture and display this information, the concepts of Is Used In and Uses are employed.

Examples:

Where this Field Is Used In a Panel, which in turn Is Used In a Screen, and so forth.

Where this Trigger Uses a Field, which Uses an Option List.

The Workflow Dependency Tool is accessed by clicking the Check Dependencies button on either the Field Management page or the Trigger Management page.

The list of dependencies is displayed in a cascading tree view, beginning with the system component from which the tool was accessed. Use the expand icon to view either the Is Used In dependency list or the Uses dependency list.

The dependency results are first grouped by component type, then displayed in alphabetical order. Use the expand and collapse icons to navigate throughout the dependency tree view.

Hovering over the component Code displays a hyperlink which, once clicked, navigates the user directly to the Management Page for that particular component in a new browser window.

Hovering over the component Label creates a hyperlink which, once clicked, refreshes the Workflow Dependency Tool to make the selected component the new root of the tree view. The list of dependencies is updated accordingly.

Check Field Dependencies

Upon clicking Check Dependencies from the Field Management page, the Workflow Dependency Tool opens in a separate browser window. The following format is followed to display how a field Is Used In other system components. This is an exhaustive list of dependency types supported by the system. However, if no dependencies exist for a particular component type, that component grouping is omitted from the dependency view.

Field Is Used In

Click the drop-down icon to learn more about each component group.

Field Uses

Click the drop-down icon to learn more about each component group.

Check Trigger Dependencies

Upon clicking Check Dependencies from the Trigger Management Page, the Workflow Dependency Tool opens in a separate browser window. The following format is followed to display how a trigger Is Used In other system components. This is an exhaustive list of dependency types supported by the system. However, if no dependencies exist for a particular component type, that component grouping is omitted from the dependency view.

Trigger Is Used By

Click the drop-down icon to learn more about each component group.

Trigger Uses

Click the drop-down icon to learn more about each component group.